Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade python from 3.10-slim to 3.12.0b1-slim #200

Closed

Conversation

wagnerdelima
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Changes included in this PR

  • Dockerfile

We recommend upgrading to python:3.12.0b1-slim, as this image has only 69 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Some of the most important vulnerabilities in your base image include:

Severity Priority Score / 1000 Issue Exploit Maturity
low severity 150 Access Restriction Bypass
SNYK-DEBIAN12-SHADOW-1559391
No Known Exploit
low severity 150 Incorrect Permission Assignment for Critical Resource
SNYK-DEBIAN12-SHADOW-1559403
No Known Exploit
low severity 150 NULL Pointer Dereference
SNYK-DEBIAN12-SHADOW-3310897
No Known Exploit
low severity 150 Arbitrary Code Injection
SNYK-DEBIAN12-SHADOW-5423923
No Known Exploit
low severity 150 CVE-2023-4641
SNYK-DEBIAN12-SHADOW-5879156
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings


Learn how to fix vulnerabilities with free interactive lessons:

🦉 NULL Pointer Dereference

@wagnerdelima wagnerdelima deleted the snyk-fix-7f9b8671cac9ccd33afcdc77ebce02d4 branch April 18, 2024 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants